Department
The Department object is used in workflows to store department information. It can be initialized with a static value or set dynamically during the process.
The Department object serves as a data holder for department values within a workflow. It does not initiate or receive transitions (arrows) and is designed solely to hold data, not to execute logic or actions.

Features
- Stores a department (
organizational unit) value. - Value can be:
Static: Predefined in the object’s propertiesDynamic: Assigned using theAssignmentcomponent during the flow
- Often used to:
- Track the originating or target department
- Influence decisions via
Comparisonnodes - Populate form or notification templates
Usage Guidelines
-
No outgoing or incoming connectors:
TheDepartmentobject doesnotsupport flow connections.
It cannot start or continue process steps. -
Used with:
-
Assignment: to set its value dynamically. -
Comparison: to evaluate against a department condition.
UI Behavior
When the Department object is selected in the flow designer:
- The
Property Inspectorpanel displays its configuration options. - Designers can:
- Set a static department value
- Bind it to dynamic values through rules or assignments
FAQs
- What events does the Department object support?
- What is the purpose of the Department object?
- Is it safe to leave the Department object unconnected?
- How do I configure the Department object?